MAN

Section: Misc. Reference Manual Pages (7 )
Index Return to Main Contents
 

NAME

man - nroff macro package for manual pages  

SYNOPSIS

nroff -man file...  

DESCRIPTION

These macros are used to lay out reference pages for manuals.

Any text argument (t in the request summary below) may be zero to six words. Quotes may be used to include blanks in a word. The text can be empty, but unlike normal macros, the next line is not used (i.e. all text MUST be included on the same line as the macro command).

A prevailing indent distance is generally NOT remembered between successive indented paragraphs, and is reset to default value upon reaching a non-indented paragraph (i.e. at .SH, .PP, or .SS). In contrast with normal procedure, all indents (tabs) are 8 spaces (0.8i) instead of 5 (0.5i). This can be changed by modifying tmac.an.

Some nroff requests may be unsafe in conjunction with this package. However, those listed below may be used with impunity:

        .bp    begin new page
        .br    break output line
        .sp n  insert n spacing lines
        .nf    begin no-fill mode
        .fi    begin fill mode (end no-fill)

Font changes with \fF are also allowed; for example, '\fIword\fR' will italicize ``word''. Note that only letters for fonts are currently allowed (R, I, B), no numbers. You can also use \sN to change to the small font, e.g. '\s-2word\s0' will make ``word'' smaller (only when using manpager(1), however).  

REGISTERS

The only external registers available to the user are O, M, and Z. Use them as follows:

        Name    Use
        olololol    olololololololololololololololololololololololololololololololololololololololololol
        O       set to 1 on command line for ONLINE-style
        M       set to 1 in tmac.an for manpager use
        Z       set to 1 in tmac.an for debugging

Another register, X, is used internally.  

PREDEFINED STRINGS

The following strings are available:

        Symbol Name  Description
        olololololol olololol  olololololololololololololololololololololololololololololololololololololololololololol
        ``       lq   left (start) quote
        ''       rq   right (end) quote
           ux   Unix tm
                DA   current date (e.g. 16:34:00 Jan 30, 1991)
                DY   current date (e.g. Jan 30, 1991)
                CT   current date (e.g. Wed Jan 30 16:34:00 1991)
                TM   current time (e.g. 16:34:00)

They are accessed with ``\*(xx'', where xx is the name of the string.  

REQUEST SUMMARY

In the table below, t generally refers to a single text string argument, meaning to imbed blanks, enclose the string in "quotes". Commands which accept (optional) indent distances i show the default if the i is not specified.

Request         Cause  Explanation
                Break?
ololololololololololololololol olololololol olololololololololololololololololololololololololololololololololololololololol
.B t            no     Text t is bold. Quote to imbed blanks.
.BI t           no     Join words of t alternating bold and italic
.BR t           no     Join words of t alternating bold and Roman
.HP i           yes    Indented paragraph with hanging indent set
                       to i (default 0.8i).
.I t            no     Text t is italic. Quote to imbed blanks.
.IB t           no     Join words of t alternating italic and bold
.IP t i         yes    Set prevailing indent to i (default 0.8i).
                       Begin indented paragraph with hanging tag
                       given by first argument. Tag t is always
                       placed on a separate line.
.IR t           no     Join words of t alternating italic and Roman
.LP             yes    Same as .PP.
.PP             yes    Begin paragraph. Set prevailing indent 0.8i.
.R t            no     Text t is Roman. Quote to imbed blanks.
.RB t           no     Join words of t alternating Roman and bold
.RE i           yes    End of relative indent. Set prevailing
                       indent to amount i (default 0.8i).
.RI t           no     Join words of t alternating Roman and italic
.RP t           yes    Like .IP, but use relative indent. Must
                       end the section with .RE.
.RS i           yes    Start relative indent, move left margin
                       in distance i (default 0.8i).
.SH t           yes    Section. Quote to imbed blanks.
.SS t           yes    Subsection. Quote to imbed blanks. No
                       indent for t.
.TH n s c v d f yes    Begin page named n of chapter s; c is
                       the chapter name; d is the date of the
                       most recent change; v is version number;
                       f is format (optional) and if ONLINE, format
                       for online viewing (use .EX at the bottom).
                       Note that now you can set register ``O'' to 1
                       on the command line to do ONLINE/EX instead.
                       Sets prevailing indent and tabs 0.8i.
 

CONVENTIONS

A typical manual page for a command or function is laid out as follows:
 

.TH TITLE [1-8]

The name of the command or function in upper-case, which serves as the title of the manual page. This is followed by the number of the section in which it appears. As an extension, if the sixth argument is ``ONLINE'', then the manual page is set up for online use, i.e. there are no page headers or footers. In this case, end the manpage with a .EX as well (which eliminates trailing blank lines to fill the last page). You can also set register ``O'' on the command line (-rO1) to force ``ONLINE'' and the .EX at the end. The .EX simply tests for ``ONLINE'' and if so, exits without adding extra space to fill the last (current) page.  

.SH NAME

name - one-line summary

The name, or list of names, by which the command is called, followed by a dash and then a one-line summary of the action performed. All in Roman font, this section contains no nroff(1) commands or escapes, and no macro requests. It is used to generate the whatis(1) database so it should be clean.  

.SH SYNOPSIS

Commands:

The syntax of the command and its arguments as typed on the command line. When in boldface, a word must be typed exactly as printed. When in italics, a word can be replaced with text that you supply. Syntactic symbols appear in Roman face: An argument, when surrounded by brackets is optional.
Arguments separated by a vertical bar are exclusive. You can supply only item from such a list. Arguments followed by an elipsis can be repeated. When an elipsis follows a bracketed set, the expression within the brackets can be repeated.

Functions:

If required, the data declaration, or ``#include'' directive, is shown first, followed by the function declaration. Otherwise, the function declaration is shown.
 

.SH DESCRIPTION

A narrative description of the command or function in detail, including how it interacts with files or data, and how it handles the standard input, standard output and standard error.

Filenames, and references to commands or functions described elswhere in the manual, are italicised. The names of options, variables and other literal terms are in boldface.  

.SH OPTIONS

For commands, the list of options along with a description of how each affects the command's operation.  

.SH ARGUMENTS

For functions, the list of its arguments along with a description of how each affects the function's operation.  

.SH FILES

A list of files associated with the command or function.  

.SH ENVIRONMENT

Any shell environment variables which may effect the operation of the command (or function).  

'.SH SEE ALSO'

A comma-separated list of related manual pages, followed by references to other published materials. This section contains no nroff(1) escapes or commands, and no macro requests.  

.SH DIAGNOSTICS

A list of diagnostic messages and an explanation of each.  

.SH NOTES

Any additional notes such as installation dependent functionality.  

.SH BUGS

A description of limitations, known defects, and possible problems associated with the command or function.  

.SH AUTHOR

The program's author and any pertinent release info.  

.SH VERSION

The program's current version number and release date.  

EXAMPLE

The following illustrates some of the requests available with this macro package:

.\" this is a comment
.TH DEMO 1 "Commands Manual" "Version 1.0" "\*(DA"
.SH NAME
demo \- show how to use -man package  \" this is a comment
.SH SYNOPSIS
.B demo
[
.I options
]
.I file
.SH DESCRIPTION
This is a test for showing how to use the
.BR nroff (1)
man package.
It shows how to use .TH, .SH, .PP, .I, and .IP commands.
.PP
This will be a new paragraph.
You can also use normal
.BR nroff (1)
commands in the text.
.SS NROFF COMMANDS:
.IP '\\"'
This is the comment command.
Note how you have to quote this sucker!
You'll probably never have to write an
.BR nroff (1)
manpage, so don't worry about it.
.IP nf
No fill mode (the normal mode is fill mode where things
get justified right and left).
.IP fi
Re-enter fill mode.
.IP br
Break line here no matter what.
.IP sp
Vertical space (also causes a break to occur).
.sp
Note that to continue an indent and make a new paragraph (as
is the case here), just put in a space (.sp).
.PP
Now we should be at a new paragraph.

Executing ``nroff -man demo.man'' results in the following output:

DEMO (1)                Commands Manual                DEMO (1)

NAME
     demo - show how to use -man package

SYNOPSIS
     demo [ options ] file

DESCRIPTION
     This is a test  for  showing  how  to  use the nroff(1)
     man package.    It  shows how to use .TH, .SH, .PP, .I,
     and .IP commands.

     This will be a new paragraph.  You can also use  normal
     nroff(1) commands in the text.

     NROFF COMMANDS:

     \"
          This is the comment command.  Note how you have to
          quote this  sucker!  You'll probably never have to
          write an nroff(1)  manpage,  so  don't worry about
          it.

     nf
          No  fill  mode (the normal mode is fill mode where
          things get justified right and left).

     fi
          Re-enter fill mode.

     br
          Break line here no matter what.

     sp
          Vertical space (also causes a break to occur).

          Note that to continue an indent  and  make  a  new
          paragraph  (as  is  the  case here), just put in a
          space (.sp).

     Now we should be at a new paragraph.

Version 1.0             23:33:57 2/25/90                     1


 

FILES

\lib\tmac\tmac.an  

BUGS

.IP does not place short tags on same line.
No .TP, .DT, .PD.
.IX ignored.
No \*R (macros and strings share namespace).
Probably others, but more than likely inconsequential.  

SEE ALSO

nroff(1), man(1), manpager(1)  

AUTHOR

Written for nroff v1.10p5 and manpager v1.41 for for Atari ST (TOS) and Minix by Bill Rosenkranz.

net:    rosenkra@convex.com
CIS:    71460,17
GENIE:  W.ROSENKRANZ
 

VERSION

man.7 1.10p5 91/2/24


 

Index

NAME
SYNOPSIS
DESCRIPTION
REGISTERS
PREDEFINED STRINGS
REQUEST SUMMARY
CONVENTIONS
.TH TITLE [1-8]
.SH NAME
.SH SYNOPSIS
.SH DESCRIPTION
.SH OPTIONS
.SH ARGUMENTS
.SH FILES
.SH ENVIRONMENT
'.SH SEE ALSO'
.SH DIAGNOSTICS
.SH NOTES
.SH BUGS
.SH AUTHOR
.SH VERSION
EXAMPLE
FILES
BUGS
SEE ALSO
AUTHOR
VERSION

This document was created by man2html, using the manual pages.
Time: 03:58:30 GMT, September 10, 2022